chore: add renovatebot, remove dependabot - #28870

Issue number: Internal

What is the current behavior?

The team would like to have dependencies managed for our E2E test applications. The goal is to let us catch issues such as #28846 shortly after the dependency is released instead of waiting for developers to report issues.

What is the new behavior?

I made two changes:

1. Added a renovate.json config that watches JS Framework dependencies (as tooling such as Vite) in our E2E test applications. I decided to start with these dependencies for now since we tend to watch those on other repos such as Ionic Docs.
2. We have other dependencies managed by Dependabot. Rather than have 2 dependency managers running, I decided to move the existing Dependabot config to Renovatebot. The same dependencies will be managed, but I did group related deps in the same group. This means that we will, for example, be able to review multiple Stencil deps updates in a single PR.

Does this introduce a breaking change?

• Yes
• No

Other information